Ddr5 pmic interface protocol and operation

ABSTRACT

An apparatus including a host interface and a power management interface. The host interface may be configured to receive control words from a host. The power management interface may be configured to (i) enable the host to read/write data from/to a power management circuit of a dual in-line memory module, (ii) communicate the data, (iii) generate a clock signal and (iv) communicate an interrupt signal. The power management interface is disabled at power on. The apparatus is configured to (i) decode the control words, (ii) enable the power management interface when the control words provide an enable command and (iii) perform a response to the interrupt signal. The clock signal may operate independently from a host clock.

FIELD OF THE INVENTION

The invention relates to memory generally and, more particularly, to amethod and/or apparatus for implementing a DDR5 PMIC interface protocoland operation.

BACKGROUND

Power management in conventional double data rate memory modules relieson discrete devices (i.e., a controller, voltage regulators, diodes andvarious passive components) implemented on a memory controller locatedon a host device (i.e., a motherboard). Power management performed bythe memory controller would be shared for all of the memory modules.Conventional double data rate memory modules use of an I²C bus to reporttemperature sensor measurements to a host memory controller. Powermeasurements are not available for memory modules.

Integrating power measurement functionality into a single chip that isfully programmable would accommodate density scaling, power sequencing,voltage margining and storage class memory support. However, accessingpower measurements on a conventional bus would be slow and can result inlatency when there are bandwidth issues.

It would be desirable to implement a DDR5 PMIC interface protocol andoperation.

SUMMARY

The invention concerns an apparatus comprising a host interface and apower management interface. The host interface may be configured toreceive control words from a host. The power management interface may beconfigured to (i) enable the host to read/write data from/to a powermanagement circuit of a dual in-line memory module, (ii) communicate thedata, (iii) generate a clock signal and (iv) communicate an interruptsignal. The power management interface is disabled at power on. Theapparatus is configured to (i) decode the control words, (ii) enable thepower management interface when the control words provide an enablecommand and (iii) perform a response to the interrupt signal. The clocksignal may operate independently from a host clock.

BRIEF DESCRIPTION OF THE FIGURES

Embodiments of the invention will be apparent from the followingdetailed description and the appended claims and drawings in which:

FIG. 1 is a diagram illustrating an example embodiment of a memorysystem;

FIG. 2 is a block diagram illustrating a memory module of FIG. 1;

FIG. 3 is a diagram illustrating a registered clock driver (RCD) inaccordance with an embodiment of the invention;

FIG. 4 is a diagram illustrating a block diagram of a power managementintegrated circuit in accordance with an embodiment of the invention;

FIG. 5 is a diagram illustrating a pinout diagram of a power managementintegrated circuit;

FIG. 6 is a diagram illustrating a I²C/I³C bus between a host memorycontroller and memory modules;

FIG. 7 is a diagram illustrating a graph of power efficiency;

FIG. 8 is a diagram illustrating a graph of a voltage ripple for a noload condition; and

FIG. 9 is a diagram illustrating a graph of a voltage ripple for a loadcondition;

FIG. 10 is a flow diagram illustrating a method for enabling a RCD-PMICinterface;

FIG. 11 is a flow diagram illustrating a method for performing a PMICread/write operation;

FIG. 12 is a flow diagram illustrating a method for performing a pollingoperation;

FIG. 13 is a flow diagram illustrating a method for selecting a lowpower operation mode;

FIG. 14 is a flow diagram illustrating a method for performing aresponse type to an interrupt signal; and

FIG. 15 is a flow diagram illustrating a method for responding to aninterrupt event.

DETAILED DESCRIPTION OF THE EMBODIMENTS

Embodiments of the present invention include providing a DDR5 RCD toPMIC interface protocol and operation that may (i) enable a powermanagement integrated circuit to be implemented on each memory module,(ii) enable a memory controller to have access to power and currentreadings for each memory module, (iii) operate using an independentclock, (iv) provide a bi-directional interrupt, (v) reduce a latency ofcommunicating power readings, (vi) reduce bandwidth on a systemmanagement bus, (vii) enable periodic polling, and/or (viii) beimplemented as one or more integrated circuits.

Referring to FIG. 1, a diagram of a memory system is shown in accordancewith an example embodiment of the invention. In various embodiments, thememory system includes a number of circuits 50 a-50 n. The circuits 50a-50 n may be implemented as memory modules (or boards). In an example,the circuits 50 a-50 n may be implemented as dual in-line memory modules(DIMMs). In some embodiments, the circuits 50 a-50 n may be implementedas double data rate fourth generation (DDR4) synchronous dynamicrandom-access memory (SDRAM) modules. In some embodiments, the circuits50 a-50 n may be implemented as double data rate fifth generation (DDR5)SDRAM modules.

In various embodiments, the circuits 50 a-50 n may comprise a number ofblocks (or circuits) 70 a-70 n, a number of blocks (or circuits) 72 a-72n, a block (or circuit) 74, a block (or circuit) 100 and/or variousother blocks, circuits, pins, connectors and/or traces. The circuits 70a-70 n may be configured as data buffers. The circuits 72 a-72 n mayimplement memory devices. In an example, the circuits 72 a-72 n may beimplemented as synchronous dynamic random-access memory (SDRAM) devices(or chips, or modules). The circuit 74 may be implemented as aregistered clock driver (RCD). In an example, the RCD circuit 74 may beimplemented as a DDR4 RCD circuit. In another example, the RCD circuit74 may be implemented as a RCD circuit compliant with the DDR5 standard.The circuit 100 may be implemented as a power management integratedcircuit (PMIC). The type, arrangement and/or number of components of thememory modules 50 a-50 n may be varied to meet the design criteria of aparticular implementation.

The memory modules 50 a-50 n are shown connected to a block (or circuit)20. The circuit 20 may implement a memory controller. The circuit 20 maybe located in another device, such as a computing engine. Variousconnectors/pins/traces 60 may be implemented to connect the memorymodules 50 a-50 n to the memory controller 20. In some embodiments, theconnectors/pins/traces 60 may be a 288-pin configuration. In an example,the memory controller 20 may be a component of a computer motherboard(or main board). In another example, the memory controller 20 may be acomponent of a microprocessor. In yet another example, the memorycontroller 20 may be a component of a central processing unit (CPU).

In an example, some of the connectors/pins/traces 60 may be part of thememory modules 50 a-50 n and some of the connectors/pins/traces 60 maybe part of the motherboard and/or memory controller 20. The memorymodules 50 a-50 n may be connected to the computer motherboard (e.g., bypins, traces and/or connectors 60) to transfer data between componentsof a computing device and the memory modules 50 a-50 n. In someembodiments, the connectors/pins/traces 60 may implement an 80-bit bus.In an example, the memory controller 20 may be implemented on anorthbridge of the motherboard and/or as a component of a microprocessor(e.g., an Intel CPU, an AMD CPU, an ARM CPU, etc.). The implementationof the memory controller 20 may be varied according to the designcriteria of a particular implementation.

In various embodiments, the circuits 50 a-50 n may be implemented asDDR4 (or DDR5) SDRAM memory modules. In an example, the circuits 50 a-50n may have a memory module density of 512 gigabyte (GB), one terabyte(TB), or higher per module (e.g., compared to 128 GB per dual in-linememory module (DIMM) in DDR3). In embodiments implementing DDR4 SDRAMmemory modules, the circuits 50 a-50 n may operate at voltages of1.2-1.4 volts (V) with a frequency between 800-4266 megahertz (MHZ)(e.g., compared to 1.5-1.65V at frequencies between 400-1067 MHZ inDDR3). In embodiments implementing DDR5 standard SDRAM memory modules,the circuits 50 a-50 n may operate with a frequency of 4.4 GHz, 6.6 GHzand/or higher frequencies. In embodiments implementing DDR5 standardSDRAM memory modules, there may be 5 memory modules on each side of theRCD 74. In some embodiments, the circuits 50 a-50 n may be implementedas low voltage DDR4 memory modules and operate at 1.05V. For example, inembodiments implementing low voltage DDR4 SDRAM memory modules, thecircuits 50 a-50 n may implement 35% power savings compared to DDR3memory. In embodiments implementing DDR4 SDRAM memory modules, thecircuits 50 a-50 n may transfer data at speeds of 2.13-4.26giga-transfers per second (GT/s) and higher (e.g., compared to 0.8-2.13GT/s in DDR3). The operating parameters of the memory modules 50 a-50 nmay be varied according to the design criteria of a particularimplementation.

In an example, the memory modules 50 a-50 n may be compliant with theDDR4 specification entitled “DDR4 SDRAM”, specification JESD79-4A,November 2013, published by the Joint Electron Device EngineeringCouncil (JEDEC) Solid State Technology Association, Arlington, Va.Appropriate sections of the DDR4 specification (e.g., the DDR4 JEDECspecification) are hereby incorporated by reference in their entirety.In another example, the memory modules 50 a-50 n may be implementedaccording to a fifth generation (DDR5) standard (e.g., for which astandard is currently under development by JEDEC). References to theDDR5 standard may refer to a latest working and/or draft version of theDDR5 specification published and/or distributed to committee members byJEDEC as of March 2018. Appropriate sections of the DDR5 standard arehereby incorporated by reference in their entirety.

In some embodiments, the memory modules 50 a-50 n may be implemented asDDR4 load reduced DIMM (LRDIMM). The data buffers 70 a-70 n may allowthe memory modules 50 a-50 n to operate at higher bandwidth and/or athigher capacities compared to DDR4 RDIMM (e.g., 2400 or 2666 MT/s forDDR4 LRDIMM compared to 2133 or 2400 MT/s for DDR4 RDIMM at 384 GBcapacity). For example, compared to DDR4 RDIMM configurations, the DDR4LRDIMM configuration of the memory modules 50 a-50 n may allow improvedsignal integrity on data signals and/or better intelligence and/orpost-buffer awareness by the memory controller 20.

Referring to FIG. 2, a block diagram is shown illustrating a memorymodule 50 a of FIG. 1. The memory module 50 a may be representative ofthe memory modules 50 b-50 n. The memory module 50 a is showncommunicating with the memory controller 20. The memory controller 20 isshown as part of a block (or circuit) 10. The circuit 10 may be amotherboard (or main board), or other electronic component or computingengine that communicates with the memory module 50 a.

The memory module 50 a may comprise one or more blocks (or circuits) 80a-80 n, the RCD circuit 74 and/or the PMIC 100. The circuits 80 a-80 nmay implement data paths of the memory module 50 a. For example, thedata path 80 a may include a block 82 a and/or the data buffer 70 a. Thedata paths 80 b-80 n may have similar implementations. In the exampleshown, the memory module 50 a may comprise five data paths (e.g., 80a-80 e) on one side of the RCD 74 and five data paths (e.g., 80 j-80 n)on another side of the RCD 74. The circuits 82 a-82 n may each beimplemented as a memory channel. Each of the memory channels 82 a-82 nmay comprise a number of blocks (or circuits) 84 a-84 n. The circuits 84a-84 n may be implemented as random access memory (RAM) chips. Forexample, the RAM chips 84 a-84 n may implement a volatile memory such asdynamic RAM (DRAM). The RAM chips 84 a-84 n may be the SDRAM devices 72a-72 n (e.g., the chips 84 a-84 n may comprise one or more of thecircuits 72 a-72 n located within one of the memory channels 82 a-82 n).In some embodiments, the RAM chips 84 a-84 n may be physically locatedon both sides (e.g., the front and back) of the circuit board of thememory modules 50 a-50 n. A capacity of memory on the memory module 50 amay be varied according to the design criteria of a particularimplementation.

The memory controller 20 may generate a signal (e.g., CLK), a number ofcontrol signals (e.g., ADDR/CMD) and/or a number of commands. The signalCLK and/or the signals ADDR/CMD may be presented to the RCD circuit 74.The commands may be presented to the PMIC 100 via a bus 104. A data bus30 may be connected between the memory controller 20 and the data paths80 a-80 n. The memory controller 20 may generate and/or receive datasignals (e.g., DQa-DQn) and data strobe signals (e.g. DQSa-DQSn) thatmay be presented/received from the data bus 30. Portions of the signalsDQa-DQn and DQSa-DQSn may be presented to respective data paths 80 a-80n.

The RCD circuit 74 may be configured to communicate with the memorycontroller 20, the data buffers 70 a-70 n, the memory channels 82 a-82 nand/or the PMIC 100. The RCD circuit 74 may decode instructions (e.g.,control words) received from the memory controller 20. For example, theRCD circuit 74 may receive register command words (RCWs). In anotherexample, the RCD circuit 74 may receive buffer control words (BCWs). TheRCD circuit 74 may be configured to train the DRAM chips 84 a-84 n, thedata buffers 70 a-70 n and/or command and address lines between the RCDcircuit 74 and the memory controller 20. For example, the RCWs may flowfrom the memory controller 20 to the RCD circuit 74. The RCWs may beused to configure the RCD circuit 74.

The RCD circuit 74 may be used in both LRDIMM and RDIMM configurations.The RCD circuit 74 may implement a 32-bit 1:2 command/address register.The RCD circuit 74 may support an at-speed bus (e.g., a BCOM bus betweenthe RCD circuit 74 and the data buffers 70 a-70 n). The RCD circuit 74may implement automatic impedance calibration. The RCD circuit 74 mayimplement command/address parity checking. The RCD circuit 74 maycontrol register RCW readback. In some embodiments, the RCD circuit 74may implement a 1 MHz inter-integrated circuit (I²C) bus (e.g., a serialbus). In some embodiments, the RCD circuit 74 may implement a 12.5 MHzinter-integrated circuit (I³C) bus. Inputs to the RCD circuit 74 may bepseudo-differential using external and/or internal voltages. The clockoutputs, command/address outputs, control outputs and/or data buffercontrol outputs of the RCD circuit 74 may be enabled in groups andindependently driven with different strengths.

The RCD circuit 74 may receive the signal CLK and/or the signalsADDR/CMD from the memory controller 20. Various digital logic componentsof the RCD circuit 74 may be used to generate signals based on thesignal CLK and/or the signals ADDR/CMD and/or other signals (e.g.,RCWs). The RCD circuit 74 may also be configured to generate a signal(e.g., CLK′) and signals (e.g., ADDR′/CMD′). For example, the signalCLK′ may be a signal Y_CLK in the DDR4 specification. The signal CLK′and/or the signals ADDR′/CMD′ may be presented to each of the memorychannels 82 a-82 n. For example, the signals ADDR′/CMD′ and CLK′ may betransmitted on a common bus 52 and a common bus 54, respectively. TheRCD circuit 74 may generate one or more signals (e.g., DBC). The signalsDBC may be presented to the data buffers 70 a-70 n. The signals DBC mayimplement data buffer control signals. The signals DBC may betransmitted on a common bus 56 (e.g., a data buffer control bus).

The data buffers 70 a-70 n may be configured to receive commands anddata from the bus 56. The data buffers 70 a-70 n may be configured togenerate/receive data to/from the bus 30. The bus 30 may comprisetraces, pins and/or connections between the memory controller 20 and thedata buffers 70 a-70 n. A bus 58 may carry the data between each of thedata buffers 70 a-70 n and respective memory channels 82 a-82 n. Thedata buffers 70 a-70 n may be configured to buffer data on the buses 30and 58 for write operations (e.g., data transfers from the memorycontroller 20 to the corresponding memory channels 82 a-82 n). The databuffers 70 a-70 n may be configured to buffer data on the buses 30 and58 for read operations (e.g., data transfers from the correspondingmemory channels 82 a-82 n to the memory controller 20).

The data buffers 70 a-70 n may exchange data with the DRAM chips 84 a-84n in small units (e.g., 4-bit nibbles). In various embodiments, the DRAMchips 84 a-84 n may be arranged in multiple (e.g., two) sets. For twoset/two DRAM chip (e.g., 84 a-84 b) implementations, each set maycontain a single DRAM chip (e.g., 84 a or 84 b). Each DRAM chip 84 a-84b may be connected to the respective data buffers 70 a-70 n through anupper nibble and a lower nibble. For two set/four DRAM chip (e.g., 84a-84 d) implementations, each set may contain two DRAM chips (e.g., 84a-84 b or 84 c-84 d). A first set may be connected to the respectivedata buffers 70 a-70 n through the upper nibble. The other set may beconnected to the respective data buffers 70 a-70 n through the lowernibble. For two set/eight DRAM chip (e.g., 84 a-84 h) implementations,each set may contain four of the DRAM chips 84 a-84 h. A set of fourDRAM chips (e.g., 84 a-84 d) may connect to the respective data buffers70 a-70 n through the upper nibble. The other set of four DRAM chips(e.g., 84 e-84 h) may connect to the respective data buffers 70 a-70 nthrough the lower nibble. Other numbers of sets, other numbers of DRAMchips, and other data unit sizes may be implemented to meet the designcriteria of a particular implementation.

The DDR4 LRDIMM configuration may reduce a number of data loads toimprove signal integrity on a data bus (e.g., the bus 30) of the memorymodule from a maximum of several (e.g., four) data loads down to asingle data load. The distributed data buffers 70 a-70 n may allow DDR4LRDIMM designs to implement shorter I/O trace lengths compared to DDR3LRDIMM designs, which use a centralized memory buffer. For example,shorter stubs connected to the memory channels 82 a-82 n may result inless pronounced signal reflections (e.g., improved signal integrity). Inanother example, the shorter traces may result in a reduction in latency(e.g., approximately 1.2 nanoseconds (ns), which is 50% less latencythan DDR3 buffer memory). In yet another example, the shorter traces mayreduce I/O bus turnaround time. For example, without the distributeddata buffers 70 a-70 n (e.g., in DDR3 memory applications) traces wouldbe routed to a centrally located memory buffer, increasing trace lengthsup to six inches compared to the DDR4 LRDIMM implementation shown inFIG. 2.

In some embodiments, the DDR4 LRDIMM configuration may implement nine ofthe data buffers 70 a-70 n. The memory modules 50 a-50 n may implement 2millimeter (mm) frontside bus traces and backside traces (e.g., theconnectors/pins/traces 60). A propagation delay through the data buffers70 a-70 n may be 33% faster than through a DDR3 memory buffer (e.g.,resulting in reduced latency). In some embodiments, the data buffers 70a-70 n may be smaller (e.g., a reduced area parameter) than a databuffer used for DDR3 applications.

An interface 102 is shown. The interface 102 may be configured to enablecommunication between the RCD circuit 74 and the PMIC 100. For example,the interface 102 may implement a register clock driver/power managementintegrated circuit interface (e.g., a RCD-PMIC interface). The interface102 may comprise one or more signals and/or connections. Some of thesignals and/or connections implemented by the interface 102 may beunidirectional. Some of the signals and/or connections implemented bythe interface 102 may be bidirectional. The interface 102 may be enabledby the host memory controller 20. In one example, the memory controller20 may enable the interface 102 for the RCD using the signal ADDR/CMD.In another example, the memory controller 20 may enable the interface102 for the PMIC 100 by presenting an enable command.

The bus 104 may be implemented as a host interface bus. The hostinterface bus 104 may be bi-directional. The host interface bus 104 maybe configured to communicate commands and/or other data to the PMIC 100and/or other components of the memory module 50 a. In some embodiments,the bus 104 may communicate with the RCD 74. In some embodiments, thehost interface bus 104 may implement an I²C protocol. In someembodiments, the host interface bus 104 may implement an I³C protocol.The protocol implemented by the host interface 104 may be variedaccording to the design criteria of a particular implementation.

Referring to FIG. 3, a diagram is shown illustrating a registered clockdriver in accordance with an embodiment of the invention. In variousembodiments, a circuit 74 may implement a registered clock drivercircuit (or chip). In various embodiments, the circuit 74 may be JEDECcompliant (e.g., compliant with the DDR4 specification entitled “DDR4SDRAM”, specification JESD79-4A, November 2013, published by the JointElectron Device Engineering Council (JEDEC) Solid State TechnologyAssociation, Arlington, Va. and/or compliant with the DDR5 standard).

The circuit 74 may have an input 160 that receives input data (e.g.,INPUTS), an input 162 that receives the clock signal CLK, aninput/output 164 that may receive/transmit control information (e.g.,DBC), outputs 166 a and 166 b that may provide data outputs (e.g., the Qoutputs QA and QB, respectively), outputs 168 a and 168 b that mayprovide output clock signals (e.g., Y_CLK) and/or inputs/outputs 170a-170 c that may send/receive data via the interface 102. The signalsINPUTS and CLK may be received from a memory controller (e.g., thememory controller 20 in FIG. 1) via a memory bus of a motherboard. In anexample, the signals INPUTS may be pseudo-differential using an externalor internal voltage reference. The signals INPUTS may comprise theADDR/CMD signals of FIGS. 1 and 2. In an example, the signal CLK may beimplemented as differential clock signals CLK_t (true) and CLK_c(complement). The signals QA, QB, and Y_CLK may be presented to a numberof memory chips (e.g., 84 a-84 n in FIG. 2). For example, the signalsQA, QB and Y_CLK may implement an output address and control bus for aDDR4 RDIMM, DDR4 LRDIMM, DDR4 UDIMM and/or DDR5 memory module. Thesignal DBC may be implemented as a data buffer control bus.

The output 170 a may present a signal (e.g., SCL). The input/output 170b may communicate a signal (e.g., SDA). The input/output 170 c maycommunicate a signal (e.g., GSI_N). The signal SCL may be a clocksignal. The signal SDA may be a data signal. For example, the signal SDAmay communicate power data. The signal GSI_N may be an interrupt signal.The signal SDA and/or the signal GSI_N may be a bi-directional signal.The signal SCL, the signal SDA and/or the signal GSI_N may each be aportion of the information communicated using the RCD-PMIC interface102. The number of signals, the number of connections and/or the type ofdata communicated using the RCD-PMIC interface 102 may be variedaccording to the design criteria of a particular implementation.

In various embodiments the circuit 74 may comprise a block 180, blocks(or circuits) 182 a-182 b, a block (or circuit) 190 a block (or circuit)192 and/or a block (or circuit) 196. The block 180 may implement acontroller interface. The blocks 182 a and 182 b may implement outputdriver circuits. In some embodiments, the blocks 182 a and 182 b may becombined as a single output driver circuit 182. The block 190 mayimplement a PMIC interface (or port) 190. The block 192 may implementregister space. The block 196 may implement one or more counters. TheRCD circuit 74 may comprise other components (not shown). The number,type and/or arrangement of the components implemented by the RCD 74 maybe varied according to the design criteria of a particularimplementation.

The block 180 may be configured to generate a data signal (e.g., DATA)and a clock signal (e.g., MCLK). The block 180 may be configured togenerate the pair of signals (e.g., BCK_T/BCK_C), a signal (e.g., BCOM),a signal (e.g., BCKE), a signal (e.g., BODT) and/or a signal (e.g.,BVREFCA). The signals DATA and MCLK may be presented to the blocks 182 aand 182 b. In various embodiments, the signal DATA may be coupled to theblocks 182 a and 182 b by combinatorial logic (not shown). The blocks182 a and 182 b may be configured to generate the signals QA, QB andY_CLK.

In various embodiments, the signals BCK_T/BCK_C may be implemented as a2-bit signal representing a differential (e.g., true (T) andcomplementary (C) versions) clock signal for the duplex data buffers 70a-70 n. In an example, the signals BCK_T/BCK_C may represent a systemclock. In various embodiments, the signal BCOM may be implemented as a4-bit signal representing data buffer commands. However, other numbersof bits may be implemented accordingly to meet the design criteria of aparticular application. The signal BCOM may be implemented as aunidirectional signal from the RCD circuit 74 to the data buffers 70a-70 n. In an example, the signal BCOM may be implemented at a singledata rate (e.g., 1 bit per signal per clock cycle). However, aparticular command may take a different number of clock cycles totransfer information. The signal BCKE may be a function registereddedicated non-encoded signal (e.g., DCKE). The signal BODT may be afunction registered dedicated non-encoded signal (e.g., DODT). Thesignal BVREFCA may be a reference voltage for use withpseudo-differential command and control signals.

The block 190 may be configured to generate the signal SCL. The block190 may be configured to generate and/or receive the signal SDA. Theblock 190 may be configured to generate and/or receive the signal GSI_N.The block 190 may be coupled with the controller interface 180. Forexample, the PMIC interface 190 and/or the controller interface 180 maybe configured to facilitate communication between the PMIC 100 and thememory controller 20. The PMIC interface 190 may be enabled in responseto the enable command received from the host memory controller 20. In anexample, the enable command may be a VR Enable command generated by thehost memory controller 20.

The block 192 may be configured to store data. For example the block 192may comprise a number of registers used for reading from and/or writingto the RCD circuit 74. Generally, the register space 192 is coupled tothe various components of the RCD using combinational logic (not shown).The block 192 may comprise a pre-defined register space 194. Thepre-defined register space 194 may be configured to store and/orcommunicate power data received from and/or written to the PMIC 100. Thepre-defined registers 194 may store configuration data used to adjust anoperating state and/or a status of the RCD 74, the interface 102 and/orthe PMIC 100.

The block 196 may be configured as one or more counters. The counters196 may be configured to track control words received from the hostmemory controller 20. In some embodiments, the counters 196 may compriseone counter to track read operations and one counter to track writeoperations. In some embodiments, the counters 196 may comprise onecounter configured to track both read operations and write operations.The implementation of the counters 196 may be varied according to thedesign criteria of a particular implementation.

In various embodiments, the circuit 74 may be enabled to automaticallyadjust a skew time of a plurality of output pins during a manufacturingtest operation. In various embodiments, the circuit 74 may be enabled toadjust the skew time (e.g., tSkew) to within a single gate delay of areference output clock. As used herein, the term tSkew may be defined asthe phase difference between an output data signal or pin (e.g., Q) andan output clock signal or pin (e.g., Y_CLK). In an example, a DDR4registered clock driver (RCD) may have sixty-six output pins. In anotherexample, a DDR5 standard registered clock driver (RCD) may have a numberof pins defined by the DDR5 standard. However, other numbers of outputpins may be implemented to meet the design criteria of a particularimplementation (e.g., a DDR5 standard implementation).

The circuit 74 may be configured to adjust the phase of the output pinsrelative to the clock signal Y_CLK (or to respective copies of the clocksignal Y_CLK) to meet manufacturer specifications (e.g., within +/−50ps, etc.). The granularity of the phase adjustment is generallydetermined by delay elements within the circuit 74. During productiontesting, the circuit 74 may be configured to perform a trimming processin response to signals from automated test equipment and provide apass/fail indication to the automated test equipment. In variousembodiments, the circuit 74 may be utilized to implement the RCD in DDR4RDIMM, DDR4 LRDIMM, DDR4 UDIMM and/or DDR5 memory modules.

The signal SCL may be a clock signal generated by the RCD 74. The signalSCL may be a clock signal that operates independently from the systemclock signal (e.g., the signals BCK_T/BCK_C, the signal CLK and/or thesignal MCLK)). In an example, the clock signal SCL may be an I²C clockoutput from the RCD 74 to the PMIC 100 communicated over thepoint-to-point interface 102. The signal SDA may be a data signalgenerated by the RCD 74 and/or received by the RCD 74. For example, thesignal SDA may enable the host memory controller 20 to write to the PMIC100 through the RCD 74 and/or read from the PMIC 100 through the RCD 74.In an example, the power data signal SDA may be an I²c data input/outputbetween the RCD 74 and the PMIC 100 communicated over the point-to-pointinterface 102. The RCD 74 may use the interface 102 to send/receive thepower data to/from the PMIC 100. The host memory controller 20 mayperform a read operation and/or a write operation to the RCD as definedby the DDR5 standard. For example, the host memory controller 20 mayread the power data stored in the pre-defined registers 194. In anotherexample, the host memory controller 20 may write instructions for thePMIC 100 into the pre-defined registers 194.

The RCD 74 may use the interface 102 to perform periodic polling and/orinterrupt handling. The RCD 74 may use the interface 102 to communicateto the PMIC 100 that the memory module(s) 50 a-50 n are in a low poweredstate. The RCD 74 may be configured to drive the interrupt signal GSI_Nto a particular state. In one example, the RCD 74 may drive the GSI_Noutput 170 c low, to communicate to the PMIC 100 a notification that thememory modules 50 a-50 n are in a low power state. The PMIC 100 maydetect the notification from the interrupt signal GSI_N and respondaccordingly.

Referring to FIG. 4, a diagram illustrating a block diagram of the powermanagement integrated circuit 100 in accordance with an embodiment ofthe invention is shown. The PMIC 100 is shown connected to the RCD 74(e.g., via the RCD-PMIC interface 102) and/or a block (or circuit) 200.The circuit 200 may implement a Serial Presence Detect (SPD) hub. ThePMIC 100 may be implemented on each of the DIMM memory modules 50 a-50n. The PMIC 100 may be implemented according to the DDR5 SDRAM standard.The PMIC 100 may be connected to other components of the memory modules50 a-50 n (not shown). The number and/or types of devices connected withthe PMIC 100 may be varied according to the design criteria of aparticular implementation.

The PMIC 100 may have inputs 202 a-202 b that receive a voltage supply.For example, the input 202 a may receive a signal (e.g., VIN_MGMT) andthe input 202 b may receive a signal (e.g., VIN_BULK). The PMIC 100 mayhave inputs/outputs 204 a-204 c. The inputs/outputs 204 a-204 c may beI/O ports corresponding to the RCD-PMIC interface 102. For example, theinput 204 a may receive the signal SCL, the input/output 204 b maycommunicate the signal SDA and the input/output 204 c may communicatethe signal GSI_N. The PMIC 100 may have inputs 206 a-206 b that mayreceive a signal (e.g., SDA_S) and/or a signal (e.g., SCL_S). The signalSDA_S may be a data signal and the signal SCL_S may be a clock signaleach received from the SPD hub 200. The PMIC 100 may have aninput/output 208 that may communicate a signal (e.g., PWR_GOOD). Forexample, the signal PWR_GOOD may be a bi-directional signal. The PMIC100 may have a number of outputs 212 a-212 f that may present regulatedvoltages. The PMIC 100 may have other inputs and/or outputs (not shown).The number, type and/or arrangement of the inputs and/or outputs of thePMIC 100 may be varied according to the design criteria of a particularimplementation.

The PMIC 100 may comprise blocks (or circuits) 220 a-220 b, a block (orcircuit) 222, a block (or circuit) 224, a block (or circuit) 226 and/orblocks (or circuits) 228 a-228 f. The blocks 220 a-220 b may eachimplement an interface. For example, the interface 220 a may be an RCDinterface and the interface 220 b may be a host interface. The block 222may implement a Multiple-Time Programmable (MTP) and volatile memory.The block 224 may implement various components such as ananalog-to-digital converter (ADC), an oscillator and/or combinationallogic. The block 226 may implement a supply interface. The blocks 228a-228 f may implement voltage regulation modules. The PMIC 100 maycomprise other components and/or connections (not shown). The componentsof the PMIC 100 may be configured to perform power management for thememory modules 50 a-50 n. The number, type and/or arrangement of thecomponents of the PMIC may be varied according to the design criteria ofa particular implementation.

The SPD hub 200 may implement a serial presence detect protocol.Generally, one SPD hub 200 may be implemented on each of the memorymodules 50 a-50 n. Each of the SPD hubs 200 may enable the memorycontroller 20 to access information about the memory modules 50 a-50 n.For example, the SPD hub 200 may provide access to an amount of memoryinstalled, what timings to use, etc. In the example shown, the SPD hub200 may communicate the signal SDA_S and/or the signal SCL_S with thehost interface 220 b. However, many different types of data may becommunicated by the SPD hub 200. In one example, the SPD hub 200 maycommunicate using the I²C protocol. In another example, the SPD hub 200may communicate using the I³C protocol. Implementing the RCD-PMICinterface 102 may reduce an amount of bandwidth on the SPD hub 200.

The SPD hub 200 may communicate with the host memory controller 20. TheSPD hub 200 may communicate using the bus 104. The SPD hub 200 may beconfigured to present the enable command from the host memory controller20 to the PMIC 100. In an example, the signal SDA_S may communicate theenable command. The RCD interface 220 a may be enabled in response tothe enable command.

The voltage regulation modules (VRMs) 228 a-228 f may be configured toprovide regulated output voltages for the various components of thememory modules 50 a-50 n. The PMIC 100 may be configured to manage,maintain and/or adjust the output voltages. The output voltages may bepart of the power data communicated using the signal SDA on the RCD-PMICinterface 102. The PMIC 100 may perform adjustments and/or modificationsto the output voltages based on instructions received from the RCD 74and/or the host memory controller 20.

In the example shown, the VRMs 228 a-228 b may be implemented aslow-dropout (LDO) linear voltage regulators. For example, the LDO 228 amay present a 1.8V signal (e.g., to one or more of the SPD hub 200, theRCD 74 and/or temperature sensors). In another example, the LDO 228 bmay present a 1.1V signal. In the example shown, the VRMs 228 c-228 fmay be implemented as switching regulators providing a supply voltage.For example, the switching regulator 228 c may provide a 1.0V VDD supplyrail. In another example, the switching regulator 228 d may provide a1.0V VDD supply rail. In yet another example, the switching regulator228 e may provide a 1.1V VDDQ supply rail. In still another example, theswitching regulator 228 f may provide a 1.8V VPP supply rail. The amountof voltage supplied by the VRMs 228 a-228 f and/or the type of circuitryimplemented to perform the voltage regulation may be varied according tothe design criteria of a particular implementation.

The supply interface 226 may be configured to receive input power. Inthe example shown, the supply interface 226 may receive the signalVIN_MGMT and the signal VIN_BULK. The PMIC 100 may be configured toconvert the input voltages to the output voltages to provide a stableand/or reliable power supply to the various components of the memorymodules 50 a-50 n.

The block 224 may comprise various components of the PMIC 100. The block224 may comprise an analog to digital converter, an oscillator and/orlogic. In one example, the logic of the block 224 may enable theRCD-PMIC interface 102 in response to the enable command received fromthe SPD hub 200.

The memory 222 may be configured to store the power management data. Thememory 222 may comprise a number of registers. The registers in thememory 222 may be read by the RCD 74 and/or written to by the RCD 74.For example, the registers in the memory 222 may be configured to storepower measurement information, current consumption information, statusinformation about the PMIC 100 and/or temperature information. Theregisters of the memory 222 may be configured to store the power dataand/or store write operations forwarded by the RCD 74 from the hostmemory controller 20. Various bits stored by the registers in the memory222 may cause the PMIC 100 to adjust a mode of operation and/or variouscharacteristics of the PMIC 100. The type of data stored in the memory222 may be varied according to the design criteria of a particularimplementation.

The RCD interface port 220 a may be configured to receive the clocksignal SCL from the RCD-PMIC interface 102. The RCD interface 220 a maybe configured to communicate the power data signal SDA from the RCD-PMICinterface 102 (e.g., bi-directional). The RCD interface 220 a may beconfigured to communicate the interrupt signal GSI_N from the RCD-PMICinterface 102 (e.g., bi-directional). The RCD interface 220 a may beconfigured to enable bi-directional communication of the power data. TheRCD interface 220 a may be disabled when the PMIC 100 is powered on(e.g., when the modules 50 a-50 n are powered on when a computer isturned on). The RCD interface 220 a may be enabled in response to theenable command received from the host memory controller 20. In anexample, the enable command may be a VR Enable command generated by thehost memory controller 20. The RCD interface 220 a may be configured toenable power management for the memory modules 50 a-50 n. In someembodiments, the RCD interface 220 a may be configured to implement anI²C protocol.

The host and/or control interface 220 b may be configured to enable thePMIC 100 to communicate with the host memory controller 20. The hostinterface 220 b may be configured to receive and/or decode the enablecommand from the signal SDA_S received at the input 206 a and/or thesignal SCL_S received at the input 206 b. The PMIC 100 may activate theRCD interface port 220 a (and the RCD-PMIC interface 102) in response tothe enable command.

The RCD-PMIC interface 102 may implement an I²C bus. For example, theRCD-PMIC interface 102 may operate at up to 1 MHz. The RCD-PMICinterface 102 may implement the signal SCL and the signal SDA at the I²Cbus frequency. The interrupt signal GSI_N may implement an interruptoutput and/or command input. By default, the RCD-PMIC interface 102 maybe disabled. The host memory controller 20 may enable the PMIC interface190 (shown in association with FIG. 3) and/or the RCD interface 220 a toenable the RCD-PMIC interface 102. For example, the memory controller 20may enable the RCD interface 220 a via the primary host interface 220 b.

The PMIC 100 may be configured to drive the interrupt signal GSI_N to aparticular state. In one example, the PMIC 100 may drive the GSI_Noutput low to communicate to the RCD 74 an event interrupt. The RCD 74may detect the event interrupt from the interrupt signal GSI_N andrespond to the event accordingly. In some embodiments, both devices mayattempt to communicate the interrupt signal GSI_N at the same time. Inan example, the RCD 74 and the PMIC 100 may both attempt to drive thesignal GSI_N low. When both the RCD 74 and the PMIC 100 attempt to drivethe signal GSI_N low, neither device may take any action and both maywait (e.g., the RCD 74 may be in a low power state). Eventually, the RCD74 may come out of the low power state and detect the event interruptgenerated by the PMIC 100.

The RCD 74 is shown presenting a signal (e.g., ALERT_N). The RCD 74 maygenerate the signal ALERT_N when the signal GSI_N is detected. Thesignal ALERT_N may be presented to the host memory controller 20. In anexample, the RCD 74 may drive the signal ALERT_N low when the interruptsignal GSI_N is detected as low at the input 170 c. The signal ALERT_Nmay be asserted due to a persistent detection of the signal GSI_N.

The RCD-PMIC interface 102 may enable the memory controller 20 to haveaccess to live power data for each of the memory modules 50 a-50 n. Inresponse to the power data, the memory controller 20 may adjust anamount of bandwidth and/or adjust access patterns to the DRAM modules 72a-72 n. The RCD-PMIC interfaced 102 may enable the RCD 74 to communicateto the PMIC 100 that the RCD 74 is in a low power state. The PMIC 100may perform power management to improve performance (e.g., reduce powerconsumption) in response to the RCD 74 being in the low power state. TheRCD-PMIC interface 102 may enable ripple voltage optimization in lowpower modes.

Referring to FIG. 5, a diagram illustrating a pinout diagram of thepower management integrated circuit 100 is shown. A top view of themicrochip package of the PMIC 100 is shown. In an example, the microchippackage of the PMIC 100 may be implemented as a quad-flat no-leads (QFN)package. For example, the QFN package of the PMIC 100 may beapproximately 5 mm×5 mm in size.

A number of pins are shown for the PMIC 100. In the example shown, thePMIC 100 may be implemented having 36 pins. In an example, pin 3, pin 7,pin 21 and/or pin 25 may be used to communicate the signal VIN_BULK(e.g., the input 202 b shown in association with FIG. 4) and pin 12 maybe used to communicate the signal VIN_MGMT (e.g., the input 202 a shownin association with FIG. 4). In another example, pin 29 may be used tocommunicate the signal SCL_S (e.g., the input 206 b shown in associationwith FIG. 4), pin 30 may be used to communicate the signal SDA_S (e.g.,the input 206 a shown in association with FIG. 4) and pin 36 may be usedto communicate the signal PWR_GOOD (e.g., the input 208 shown inassociation with FIG. 4). The pinout of the PMIC 100 may be variedaccording to the design criteria of a particular implementation and/oraccording to the DDR5 standard JEDEC specification.

The RCD-PMIC interface 102 may be implemented by the PMIC 100 using theDDR5 standard JEDEC pinout with 3 additional pins. An addition 300 isshown. The addition 300 may comprise pin 31. In the example shown, pin31 may be implemented to send/receive the interrupt signal GSI_N. Anaddition 302 is shown. The addition 302 may comprise pin 10 and pin 11.In the example shown, pin 10 may be implemented to send/receive thepower data signal SDA. In the example shown, pin 11 may be implementedto receive the clock signal SCL. In the example shown, pin 10, pin 11and pin 31 may be configured to communicate the signals of the RCD-PMICinterface 102. However, any available and/or unused pins of the PMIC 100may be utilized to communicate the signals of the RCD-PMIC interface102.

Similarly, the RCD-PMIC interface 102 may be implemented by the RCD 74using the DDR5 standard JEDEC pinout with 3 additional pins. In oneexample, the interrupt signal GSI_N may be implemented at a pin H9 ofthe RCD 74. In another example, the clock signal SCL may be implementedat a pin H5 of the RCD 74. In yet another example, the power data signalSDA may be implemented at a pin H6 of the RCD 74. However, any availableand/or unused pins according to the DDR5 standard for the RCD 74 may beutilized to communicate the signals of the RCD-PMIC interface 102.

Referring to FIG. 6, a diagram illustrating a I²C/I³C bus between thehost memory controller 20 and memory modules 50 a-50 h are shown. Asystem bus 350 is shown. The system bus 350 may implement an I²C or I³Cprotocol. The system bus 350 may correspond with the host interface bus104 shown in association with FIG. 2. Generally, the system bus 350 maycommunicate with 8 DIMMs per bus (e.g., the memory modules 50 a-50 h).

The memory modules 50 a-50 h may each comprise the SPD hub 200 and/or anumber of devices 352 a-352 n. In the example shown, the SPD hub 200 aand the slave devices 352 a-352 d are shown as a representative examplecorresponding to the memory module 50 a. In an example, the slavedevices 352 a-352 d may be the PMIC 100, the RCD 74 and two temperaturesensors. A portion 350′ of the system bus 350 is shown on the memorymodule 50 a communicating between the SPD hub 200 a and the slavedevices 352 a-352 d. In some embodiments, the system bus 350 maycommunicate with at least five devices per memory module 50 a-50 h(e.g., to receive a power measurement readout, a status of the PMIC 100,a temperature readout, a status of the SPD and/or a status of the RCD74).

Since the system bus 350 may communicate with many devices, there may bebandwidth availability issues on the system bus 350. Implementing theRCD-PMIC interface 102 may reduce bandwidth congestion on the systemmanagement bus 350. The RCD-PMIC interface 102 may reduce a latency(e.g., a readout time latency) of communicating the critical power data.The power data may enable the memory controller 20 to adjust memoryaccess patterns. Implementing the RCD-PMIC interface 102 may improveDIMM performance of the memory modules 50 a-50 h by improving the outputripple of the PMIC regulator and PMIC power efficiency in low powerstate utilization.

In an example of the system bus 350 implementing the I³C protocol (e.g.,operating at 12.5 MHz), a total amount of time for a basic periodicreadout (e.g., excluding packet error check (PEC), IBI check and/orsoftware overhead) may be approximately 464 μs. For example, using onlythe system bus 350, the PMIC current/power read out time may beapproximately 128 μs (e.g., 8*16) with one PMIC per DIMM and 256 μs(e.g., 2*8*16) with two PMICs per DIMM. In another example, using onlythe system bus 350, the PMIC general status read out time may beapproximately 128 μs (e.g., 8*16) with one PMIC per DIMM and 256 μs(e.g., 2*8*16) with 2 PMICs per DIMM. In yet another example, using onlythe system bus 350, the temperature sensor (TS) read out time may be 128μs (e.g., 8*2*8) with two temperature sensors per DIMM and 48 μs (8*6)with 1 SPD TS per DIMM. In still another example, using only the systembus 350, the SPD readout time may be approximately 80 μs with 1 SPD perDIMM (e.g., likely two registers (MR48 and MR52) would be read inaddition to the SPD TS). Additionally, using only the system bus 350 mayfurther include an RCD read out time. In another example, using the I²Cbus protocol (e.g., running at 1 MHZ), the total time for the basicperiod readout may be approximately 5.5 ms.

The PMIC 100 may be configured to provide live measured power and/orcurrent consumption for each rail (e.g., on each of the voltageregulator modules 228 a-228 f and/or the outputs 212 a-212 f). Forexample, the measured power and/or current consumption may be the powerdata stored in the memory 222. The RCD 74 may be configured to retrievethe power data and store the power data in the pre-defined registers194. The RCD 74 may provide the power data to the memory controller 20.The memory controller 20 may access the power data and leverage theinformation to adjust access patterns for the DRAM modules 72 a-72 n.Accessing the power data using the system bus 350 (e.g., via the I²C/I³Cprotocol) may be slow and potentially have bandwidth issues, which addsmore latency.

Referring to FIG. 7, a diagram illustrating a graph 400 of powerefficiency is shown. A line 402 and a line 404 are shown. The line 402may represent a power consumption efficiency when the PMIC 100 receivesa notification that the entire memory module (e.g., the memory module 50a) is in a low power state. The line 404 may represent a powerconsumption efficiency without using the notification information.

In an example, the memory modules 50 a-50 n may be in a self-refreshstate and the RCD 74 and/or the data buffers 70 a-70 n may be in a clockstopped power down state. When the memory modules 50 a-50 n are in aself-refresh state and the RCD 74 and/or the data buffers 70 a-70 n arein a clock stopped power down state, the power consumption for each ofthe memory modules 50 a-50 n may be much lower. The RCD 74 may send asignal (e.g., the interrupt signal GSI_N) to the PMIC 100 to adjust theoperation of the PMIC 100. The interrupt signal GSI_N from the RCD 74 tothe PMIC 100 may provide a notification to the PMIC 100 that the memorymodule(s) 50 a-50 n are in a low power state. For example, the RCD 74may enter a clock stopped power down state and trigger the notificationto the PMIC. The output 170 c of the RCD 74 may present the interruptsignal GSI_N to the RCD-PMIC interface 102 and the PMIC 100 may receivethe signal GSI_N at the input 204 c. The RCD 74 may determine that thememory module(s) 50 a-50 n are in the lower powered state and send thenotification without instruction and/or intervention from the hostmemory controller 20 (e.g., the RCD 74 may take care of determining thestate and generating the notification alone).

Implementing the PMIC 100 may offer better efficiency (e.g.,approximately 1.5% to 2% when the notification is provided that thememory module(s) 50 a-50 n are in the low power state. In the exampleshown, the line 402 (e.g., with the PMIC 100) shows an efficiency ofapproximately 83% at a 0.1 A output load (e.g., a low power state) andthe line 404 (e.g., without the PMIC 100) shows an efficiency ofapproximately 81% at the 0.1 A output load (e.g., a difference ofapproximately 2%). In the example shown, the PMIC 100 may enableadjustments to the memory access patterns and/or frequency scaling inthe low power state. However, the PMIC 100 may enable power managementto improve efficiency in all power modes. For example, at an output loadof 1.1 A, the efficiency corresponding to the line 402 may beapproximately 87% and the efficiency corresponding to the line 404 maybe approximately 86% (e.g., a difference of 1% improvement). In anotherexample, at an output load of 2.1 A, the efficiency corresponding to theline 402 may be approximately 86.5% and the efficiency corresponding tothe line 404 may be approximately 86% (e.g., a difference of 0.5%improvement). By tweaking the power management performed by the PMIC100, additional improvements in efficiency may be achieved. The powermanagement performed by the PMIC 100 and/or the efficiency gainsachieved by the power management may be varied according to the designcriteria of a particular implementation.

Referring to FIG. 8, a diagram illustrating a graph 420 of a voltageripple is shown. The graph 420 may have an X axis representing time inμs. The graph 420 may have a Y axis representing an output voltageripple when there is no load. For example, the memory module(s) 50 a-50n may be in a low power state when there is no load. A line 422 isshown. The line 422 may represent an output voltage ripple for the PMIC100 in a no load condition.

In an example, the memory modules 50 a-50 n may be in a self-refreshstate and the RCD 74 and/or the data buffers 70 a-70 n may be in a clockstopped power down state. When the memory modules 50 a-50 n are in aself-refresh state and the RCD 74 and/or the data buffers 70 a-70 n arein a clock stopped power down state, the power consumption for each ofthe memory modules 50 a-50 n may be much lower. The interrupt signalGSI_N from the RCD 74 to the PMIC 100 may provide a notification to thePMIC 100 that the memory module(s) 50 a-50 n are in a low power state.The PMIC 100 may adjust operation in response to the notificationprovided by the interrupt signal GSI_N.

A peak 424 is shown on the line 422. The peak 424 may be atapproximately 1.2125V. A peak 426 is shown in the line 422. The peak 426may be at approximately 1.1985V. The output voltage line 422 may have apeak-to-peak voltage of approximately (1.2125V-1.1985V) 14 mV. The PMIC100 may have approximately a 14 mV ripple during a low power state(e.g., no load condition).

Referring to FIG. 9, a diagram illustrating a graph 440 of a voltageripple is shown. The graph 440 may have an X axis representing time inμs. The graph 440 may have a Y axis representing an output voltageripple when there is a 3 A load. For example, the memory module(s) 50a-50 n may not be in a low power state when there is a 3 A load. A line442 is shown. The line 442 may represent an output voltage ripple forthe PMIC 100 in a 3 A load condition.

A peak 444 is shown on the line 442. The peak 444 may be atapproximately 1.1955V. A peak 446 is shown in the line 442. The peak 446may be at approximately 1.1895V. The output voltage line 442 may have apeak-to-peak voltage of approximately (1.1955V-1.1895V) 6 mV. The PMIC100 may have approximately a 6 mV ripple during the 3 A load state.

The RCD 74 may be configured to send the interrupt signal GSI_N to thePMIC 100 to adjust the operation and/or calibrate the PMIC 100.Generally, the PMIC 100 may provide an optimized output ripple when theentire memory module(s) 50 a-50 n is in lower state. In someembodiments, the PMIC 100 may further improve the ripple outputperformance when not in the low powered state. The adjustments made bythe PMIC 100 in response to the interrupt signal GSI_N may conservepower and/or improve performance for the DRAM components 72 a-72 n.Additionally, components such as the logic components (e.g., the RCD 74,the data buffers 70 a-70 n, the NVC, etc.) may benefit from the powermanagement performed by the PMIC 100.

The RCD 74 may enable the host memory controller 20 to perform read andwrite operations to the PMIC register space (e.g., the pre-definedregisters 194) through an in-band RCW command. In an example, thepre-defined registers 194 (e.g., the PMIC register space) may range from0x00 to 0xFF (e.g., a total of 256 8-bit registers). The RCD page 0x81may be reserved for PMIC write and read operations. The address range0x60 to 0x67 may be used for the PMIC write operations. The addressrange 0x70 to 0x77 may be used for PMIC read operations. Other addressspace in the page 0x81 may be marked as reserved.

The host memory controller 20 may be configured to write to the PMIC 100through the RCD 74. To perform a write to the PMIC 100, the host memorycontroller 20 may perform a write operation (e.g., as defined by anormal write operation using the DDR5 standard) to the pre-definedregisters 194 of the RCD 74. In an example, the pre-defined registers194 may be at a location corresponding to RCD page 0x81. Example controlwords are shown in association with Table 1:

TABLE 1 RCD Page 0x81 Control Word Meaning RW60 PMIC Address A RW61 Datafor Address A RW62 PMIC Address B RW63 Data for Address B RW64 PMICAddress C RW65 Data for Address C RW66 PMIC Address D RW67 Data forAddress D RW68 Reserved . . . . . . RW6E Reserved RW6F [7:4]: Write DataStatus [3:0]: Reserved

Due to mismatch in bus speed between the host 20 and the RCD 74 (e.g.,the system bus 350) and RCD-PMIC interface 102, the host 20 may performwrite operations to up to four different addresses at a time to the PMIC100. The four addresses in the PMIC may be sequential and/or any randomorder that the host 20 desires. Generally, the RCD page 0x81 is used forwrite operation to the PMIC 100.

The control word addresses RW60 to RW67 may be used by the host memorycontroller 20 to perform write operations to the PMIC 100. The hostmemory controller 20 may provide an op code to write the PMIC address(e.g., an 8-bit address) to even control word addresses (e.g., RW60,RW62, RW64, RW66). For example, the PMIC addresses A, B, C and D may beany random address in the memory 222 of the PMIC 100. The host memorycontroller 20 may provide an op code to write the PMIC data to oddcontrol word addresses (e.g., RW61, RW63, RW65, RW67). The host memorycontroller 20 may start the write operation at the control word addressRW60 and go up (e.g., RW61, RW62, RW63, etc.) and then loop back toRW60. Some bits (e.g., [7:4]) of the control word address RW6F maycontain a write operation status for each address (e.g., to indicatewhether the write operation is complete or on-going). The control wordsand/or registers 194 used for the PMIC write operations may be variedaccording to the design criteria of a particular implementation.

The host memory controller 20 may send out the consecutive MRW commandsto the RCD 74 (e.g., like any other MRW command). The RCD 74 mayimplement the counter 196 and increment the counter 196 for each MRWcommand for PMIC write operation. The RCD 74 may allow up to four PMICwrite operation commands at a time. For each MRW command for PMIC writeoperation, the RCD 74 may generate the write command on the RCD-PMICinterface 102 (e.g., using the I²C protocol) and decrement the counter196 by one until the counter 196 reaches zero.

When the RCD counter 196 is at zero, the host 20 may start the PMICwrite operation to a pre-defined RCD address (e.g., the register address0x60). In an example, the RCD 74 may always start at the RCD address0x60 to generate the write command to the PMIC 100 when the counter 196is incremented to one.

When host 20 makes the write request to the RCD 74, the RCD 74 mayexecute the operation on the RCD-PMIC interface 102. Due to clockfrequency mismatch and/or the RCD 74 being in the middle of anotheroperation, the host 20 may not exactly know when RCD 74 has executed theoperation. For each host request, the RCD 74 may provide a status updatein the register PG81RW6F [7:4]. The host 20 may read the status and ifthe write operation is complete, the host 20 may issue another writerequest to the RCD 74.

The host memory controller 20 may be configured to read from the PMIC100 through the RCD 74. To perform a read from the PMIC 100, the hostmemory controller 20 may perform a read operation from the pre-definedregisters 194 of the RCD 74 as defined by a normal read operation usingthe DDR5 standard. In an example, the pre-defined registers 194 may beat a location corresponding to RCD page 0x81. Example control words areshown in association with Table 2:

TABLE 2 RCD Page 0x81 Control Word Meaning RW70 PMIC Address A RW71 Datafrom Address A RW72 PMIC Address B RW73 Data from Address B RW74 PMICAddress C RW75 Data from Address C RW76 PMIC Address D RW77 Data fromAddress D RW78 Reserved . . . . . . RW7E Reserved RW7F [7:4]: Read DataStatus [3:0]: Reserved

Due to mismatch in bus speed between the host 20 and the RCD 74 (e.g.,the system bus 350) and RCD-PMIC interface 102, the host 20 may performread operations from up to four different addresses at a time from thePMIC 100. The four addresses in the PMIC 100 may be sequential and/orany random order that the host 20 desires. Generally, the RCD page 0x81is used for read operation from the PMIC 100.

The control word addresses RW70 to RW77 may be used by the host memorycontroller 20 to perform read operations from the PMIC 100. The hostmemory controller 20 may generate an op code to write the PMIC address(e.g., an 8-bit address) to even control word addresses (e.g., RW70,RW72, RW74, RW76). For example, the PMIC addresses A, B, C and D may beany random address in the memory 222 of the PMIC 100. The host memorycontroller 20 may read the PMIC data from odd control word addresses(e.g., RW71, RW73, RW75, RW77). The host memory controller 20 may startthe read operation at the control word address RW70 and go up (e.g.,RW71, RW72, RW73, etc.) and loop back to RW70. Some bits (e.g., [7:4])of the control word address RW7F may contain a read operation status foreach address (e.g., to indicate whether the read operation is stillexecuting or valid data is present). The control words and/or registers194 used for the PMIC read operations may be varied according to thedesign criteria of a particular implementation.

The host 20 may send out consecutive MRW commands to the RCD 74 like anyother MRW command. The RCD 74 may implement the counter 196 andincrement the counter 196 for each MRW command for PMIC read operations.In some embodiments, the RCD 74 may implement one counter for the PMICread operations and another counter for the PMIC write operations. Insome embodiments, one counter may be implemented by the RCD 74 for boththe PMIC read operations and the PMIC write operations. The RCD 74 mayallow up to four PMIC read operation commands at a time. For each MRWcommand for PMIC read operation, the RCD 74 may generate the readcommand on the RCD-PMIC interface 102 (e.g., using the I²C protocol) anddecrement the counter 196 by one until the counter 196 reaches zero.

When the RCD counter 196 is at zero, the host 20 may start the PMIC readoperation at a pre-defined address (e.g., the address 0x70). In anexample, the RCD 74 may always start at the RCD address 0x70 to generatethe read command to the PMIC 100 when the counter 196 is incremented toone.

When host the makes the read request to the RCD 74, the RCD 74 mayexecute the operation on the RCD-PMIC interface 102. Due to clockfrequency mismatch and/or the RCD 74 being in the middle of anotheroperation, the host 20 may not exactly know when the RCD 74 has executedthe operation and has valid data in the registers 194. For each hostrequest, the RCD 74 may provide the status update in the registerPG81RW7F [7:4]. The host 20 may read the status and if valid data ispresent, the host 20 may read the data from corresponding registers(e.g., PG81RW71, PG81RW73, PG81RW75, PG81RW77, etc.). The host 20 mayread the power data by performing the normal control word read proceduredefined by the DDR5 standard.

The RCD 74 may access the PMIC register space (e.g., the memory 222).The RCD 74 may be configured to periodically poll the PMIC 100 for thegeneral status of the PMIC 100. In an example, the polling frequency maybe controlled by the register PG82RW7E [7:5]. The RCD 74 may generate aread command to the PMIC 100 to a predefined range in the memoryregister space 222 (e.g., addresses 0x08 to 0x0F and 0x33). The RCD page0x82 may be reserved for the read command that is generated internallyby the RCD 74 (e.g., without prompting from the memory module 20) andsent to the PMIC 100 due to either periodic polling and/or a GSI_Ninterrupt handling process.

The RCD 74 may be configured to periodically poll the PMIC 100 and/orhandle event interrupts received from the PMIC 100. Data acquired fromthe PMIC 100 by the RCD 74 may be stored in the pre-defined registers194. The host memory controller 20 may access the data retrieved by theRCD 74 as defined by the DDR5 standard. In one example, the pre-definedregisters 194 used by the RCD 74 to store data read by the RCD 74 fromthe PMIC 100 may be at a location corresponding to RCD page 0x82. Thehost memory controller 20 may not be allowed to write to the RCD page0x82 but may read from the registers to read the status of the PMIC 100using the normal read procedure as defined by the DDR5 standard. Examplecontrol words are shown in association with Table 3, Table 4 and Table5:

TABLE 3 RCD Page 0x82 PMIC Address Control Word Space Meaning RW60 SeeTable 4 Data Read by RCD from RW61-RW63 Reserved Periodic Polling RW640x08 RW65 0x09 RW66 0x0A RW67 0x0B RW68 0x0C RW69 0x0D RW6A 0x0E RW6B0x0F RW6C 0x31 RW6D 0x33 RW6E-RW6F Reserved RW70 See Table 4 Data Readby RCD due to RW71-RW73 Reserved GSI_N Interrupt RW74 0x08 Handling RW750x09 RW76 0x0A RW77 0x0B RW78-RW7C Reserved RW7D 0x33 RW7E RCD ConfigRegisters RW7F RCD Config Registers

TABLE 4 Page 0x82 Bits Description RW60 7 PMIC Polling Status 6:0Reserved RW70 7 GSI_N Interrupt Handling Status 6:0 Reserved

The host memory controller 20 may configure the RCD configurationregisters in the RCD 74 at power up. By default, the RCD-PMIC interface102 may be disabled.

TABLE 5 CW Bits Description RW7E 7:5 Polling Frequency 4:0 Reserved RW7F7 GSI_N Enable 6 I²C Interface Enable 5:4 I²C Interface Clock Frequency3 Reserved 2 Low Power Optimization Enable 1 Generate Mask Command whenGSI_N is asserted 0 Generate Clear Command when GSI_N is asserted

The RCD 74 may be configured to respond to the interrupt signal GSI_Nreceived from the RCD-PMIC interface 102. For example, the PMIC 100 maydrive the signal GSI_N low to indicate that an event interrupt hasoccurred. The RCD 74 may not be able to respond to some events detectedby the PMIC 100. In an example, the RCD 74 may not be able to respondbecause the RCD 74 cannot operate due to power loss (e.g., the eventdetected by the PMIC 100 may be the loss of power). A summary of eventhandling by the RCD 74 in response to the interrupt signal GSI_Npresented by the PMIC 100 is shown in Table 6 and Table 7. Table 7 alsoshows the status of the signal PWR_GOOD from the PMIC 100 for each eventas a reference. In some embodiments, the RCD 74 may not be expected todo anything related to the signal PWR_GOOD. In Table 6 and in Table 7,PG may indicate ‘Power Good’, OV may indicate ‘Over Voltage’, UV mayindicate ‘Under Voltage’ and CL may indicate ‘Current Limit’.

TABLE 6 Event Status Bits Clear Bits Mask Bits VIN_BULK PG R08 [7] R10[7] R15 [7] VIN_MGMT PG R08 [6] R10 [6] R15 [6] VIN_BULK OV R08 [0] R10[0] R15 [0] VIN_MGMT OV R08 [1] R10 [1] R15 [1] SWA-SWD PG R08 [5:2] R10[5:2] R15 [5:2] 1.8 LDO PG R09 [5] R11 [5] R16 [5] 1.1 LDO PG R33 [2]R14 [2] R19 [2] VBIAS LDO PG R09 [6] R11 [6] R16 [6] SWA-SWD OV R0A[7:4] R12 [7:4] R17 [7:4] SWA_SWD UV R0B [3:0] R13 [3:0] R18 [3:0] VBIASUV R33 [3] R14 [3] R19 [3] SWA-SWD CL R0B [7:4] R13 [7:4] R18 [7:4]SWA-SWD High R09 [3:0] R11 [3:0] R16 [3:0] Current/Power High Temp WarnR09 [7] R11 [7] R16 [7] Critical Temp N/A N/A N/A VIN_MGMT to R09 [4]R11 [4] R16 [4] VIN_BULK Switchover Valid VIN_MGMT R33 [4] R14 [4] R19[4] in Switchover

TABLE 7 VReg RCD Event Disable PWR_GOOD GSI_N Response VIN_BULK PG NoLow Low 2 VIN_MGMT PG No High Low 2 VIN_BULK OV Yes Low Low 1 VIN_MGMTOV No High Low 2 SWA-SWD PG No Low Low 2 1.8 LDO PG No Low Low 2 1.1 LDOPG No Low Low 2 VBIAS LDO PG No Low Low 2 SWA-SWD OV Yes Low Low 1SWA_SWD UV Yes Low Low 1 VBIAS UV Yes Low Low 1 SWA-SWD CL No High Low 2SWA-SWD High No High Low 2 Current/Power High Temp Warn No High Low 2Critical Temp Yes Low Low 1 VIN_MGMT to No High Low 3 VIN_MGMT SwitchVIN_MGMT to No High Low 3 VIN_MGMT Switch

Generally, the RCD 74 may perform three different categories ofresponses when the interrupt signal GSI_N is presented by the PMIC 100(e.g., GSI_N is detected as low at the input 170 c of the RCD 74). Afirst category (e.g., RCD Response 1 in Table 7) may represent asituation when power may be lost. For example, the RCD 74 may not beable to perform a response because eventually power will be lost. Asecond category (e.g., RCD Response 2 in Table 7) may comprise clearingthe corresponding PMIC register shown in Table 6. If the interruptsignal GSI_N persists, the RCD 74 may mask the PMIC register shown inTable 6. The host memory controller 20 may decide what to do next. Athird category (e.g., RCD Response 3 in Table 7) may comprise clearingthe corresponding PMIC register shown in Table 6. In each responsecategory, the RCD 74 may assert the signal ALERT_N (e.g., drive ALERT_Nlow). Clearing the PMIC register may clear the error command to the RCD.The RCD may de-assert the signal ALERT_N (RW04 code: 0xFE).

One of the pre-defined registers 194 may be an error log register.Generally, when implementing the RCD-PMIC interface 102, the RCD 74 mayutilize the same registers as defined by the DDR5 standard. A controlword (e.g., address RW24 [0]) may be used to identify a PMIC error. Whenthere is a clear PMIC error command, the RCD 74 may reset the bit in thecontrol word address RW24 [0] and stop driving the signal ALERT_N(assuming the interrupt signal GSI_N is not asserted).

In some embodiments, read operations from the PMIC 100 may be the mostfrequent operation type. For example, the PMIC 100 may use the mostamount of data reads. Since the PMIC 100 data reads may be the mostfrequent operation type, the RCD-PMIC interface 102 may be used toperform the data reads and alleviate bandwidth limitations on the systemmanagement bus 350. Implementing the RCD-PMIC interface 102 may enablethe host memory controller 20 to use the I²C protocol for the system bus350 (e.g., instead of the I³C protocol). The RCD-PMIC interface 102 mayoffer autonomous operation to improve the power efficiency and/orelectrical characteristics of the memory modules 50 a-50 n. For example,the PMIC 100 may improve power efficiency by adjusting voltage levelsand/or performing frequency scaling. In an example, the power managementmay be customized in either the RCD 74 and/or the PMIC 100.

In some embodiments, the input/output levels for the interrupt signalGSI_N and/or the power data signal SDA communicated from the RCD 74 tothe PMIC 100 may be based on a 1.1V supply and use Open Drain 1.1V I/Olevels. Since the interrupt signal GSI_N is a bi-directional signal, apullup resistor to 1.1V supply on the DIMM board may be implemented. The1.1V supply for the pullup resistor may be the same 1.1V supply that theRCD 74 may receive on VDD pins and/or be a different 1.1V supply thatthe PMIC 100 may generate from the 1.1V LDO output 212 b. The I/O levelfor the clock signal SCL from the RCD 74 to the PMIC 100 may be based onthe 1.1V supply and may be a 1.1V push pull level. In an example, thepullup resistor for the interrupt signal GSI_N may be approximately 1KOhm. The value of the pullup resistors for the signal GSI_N and/or thesignal SDA may be varied according to the design criteria of aparticular implementation.

The RCD 74 may be the master component for the I²C interface 102 for thePMIC 100. For example, the RCD 74 may implement a master I²C protocol.The RCD 74 may communicate using the standard I²C protocol to the PMIC100 regardless of what the host memory controller 20 uses to communicateto the RCD 74 (e.g., as a slave). For example, the protocol used tocommunicate between the RCD 74 and/or the host memory controller 20 maybe either I²C or I³C.

The RCD 74 may generate the clock signal SCL internally. The frequencyof the clock signal SCL may be configured through the registers 194(e.g., the register PG82RW7F [5:4]). In an example, the RCD 74 may notbe required to generate a precise output clock frequency. The outputclock frequency of the signal SCL may vary within a 50% range of theconfigured register value. The RCD 74 may source the clock signal SCLindependently from a clock input (e.g., from the host 20) to enable theRCD 74 to generate commands independently and/or to execute commandsreceived from the host 20 regardless of the state of the clock inputfrom the host 20. In an example, at first initial power on, the RCD 74does not generate the clock signal SCL. The host 20 may enable theRCD-PMIC interface 102 by setting one of the registers 194 to aparticular value (e.g., PG82RW7F [6]=‘1’). In a clock stopped power downmode, the RCD 74 may shut off the SCL output 170 a and/or the SDA I/O170 b.

The PMIC 100 may assert the interrupt signal GSI_N at any time duringnormal operation to communicate any event. The RCD 74 may respond to thePMIC 100 and the host 20 to all assertions of the interrupt signal GSI_Ndetected except for a clock stopped power down mode.

Then the RCD 74 receives the interrupt signal GSI_N, the RCD 74 mayexecute at least two steps. One step may be that the RCD 74 may assertthe signal ALERT_N to the host 20. Another step may be that the RCD 74generates a read command to the PMIC 100 to pre-defined PMIC registers(e.g., registers 0x08 to 0x0B and 0x33). Based on the data that RCD 74reads from the PMIC registers 222, the RCD 74 may decipher the eventthat caused the interrupt signal GSI_N to be asserted (e.g., by lookingat which status bit register is set). In some embodiments, the RCD 74may determine that more than one status bit registers are set. Based onwhich status bit register is set, the RCD 74 may decides which responseto take (e.g., Response 1, Response 2 and/or Response 3 as shown inassociation with Table 7). If more than one status bit register is set,the RCD 74 may execute more than one response.

For the 11 events that comprise Response 1, the PMIC 100 mayautomatically and independently trigger a VR Disable command (e.g.,disable voltage regulation). The VR Disable command may cause the RCD 74to lose power and no action is needed (or possible) by the RCD 74. Insome embodiments, the RCD 74 may attempt to read the PMIC statusregisters 222 as described above to decipher what event caused theassertion of the interrupt signal GSI_N, but eventually the RCD 74 willlose power. If the RCD 74 was able to complete the read operation anddecipher what caused the GSI_N signal assertion before power is lost,the RCD 74 may not take any further action based on these events. Thesystem host 20 may be expected to take specific action to either powercycle the PMIC 100 (e.g., if the PMIC 100 was in Secure Mode) or readthe status register 222 and try to issue a VR Enable (e.g., enablevoltage regulation) command again (e.g., if the PMIC 100 was inProgrammable Diagnostic Mode) to see if the PMIC 100 recovers.Otherwise, the host 20 may power cycle the PMIC 100 again.

For the 19 events that comprise Response 2, the read response from thePMIC 100 may be updated in the RCD registers 194 (as shown inassociation with Table 3). In an example, the RCD 74 may update thestatus in register PG82RW70 [7]. If PG82RW7F [0]=‘1’, then the RCD 74may generate a Write ‘1’ command to the corresponding Clear Bit Registerlocation as shown in Table 3 to clear the status register of the PMIC100 (e.g., indicating that the RCD 74 has deciphered which event causedthe interrupt signal GSI_N). The RCD 74 may generate a Write ‘1’ commandto the all 8 bits of the corresponding Clear register to clear theentire 8 bits of the status register.

The Write ‘1’ command may cause the PMIC 100 to stop asserting theinterrupt signal GSI_N if the event is no longer present. The RCD 74 maywait (e.g., a maximum of 5 μs) to let the PMIC 100 let go of theassertion of the interrupt signal GSI_N after generating the clearcommand. For example, the 5 μs wait time may be referenced from therising edge of the clock when the RCD 74 receives an acknowledgeindication from the PMIC 100. If the event is still present, the PMIC100 may continue to assert the interrupt signal GSI_N and the status bitwill not be cleared.

If the event is still present at the RCD 74 (e.g., after the 5 μs wait),the RCD 74 will see the signal GSI_N asserted (e.g., at the input 170c). If the register PG82RW7F [1]=‘1’, the RCD 74 may generate a Write‘1’ command to the corresponding Mask Bit Register location (shown inassociation with Table 3) to mask the interrupt signal GSI_N. In someembodiments, since the RCD 74 has already deciphered which event causedthe signal GSI_N, additional work may not be necessary. In someembodiments, the RCD 74 may read the event status to determine if theevent is the same. If the event is the same, the Write ‘1’ command tothe appropriate mask register should cause the PMIC 100 to stopasserting the signal GSI_N signal. The RCD 74 may wait (e.g., a maximumof 5 μs) to let the PMIC 100 stop assertion of the signal GSI_N aftergenerating the mask command. For example, the 5 μs time is referencedfrom the rising edge of the clock when the RCD 74 receives anacknowledge indication from the PMIC 100. When the RCD 74 generates theWrite ‘1’ command to mask the appropriate registers, the RCD 74 may notalter a mask setting that the host 20 may have programmed at initialpower on.

In some embodiments, after masking, the PMIC 100 may still assert theinterrupt signal GSI_N to the RCD 74. The RCD 74 may assume that theremay be another new event causing the assertion of the interrupt signalGSI_N. The RCD 74 may repeat reading the PMIC registers (e.g., 0x08 to0x0B and 0x33) and decide which response to take until the GSI_N signalis no longer seen asserted at the input 170 c. In some embodiments, whenthe RCD 74 repeats the PMIC register read operation, only the last readinformation may be stored in the RCD registers 194 (e.g., if the PMICstatus registers 194 are updated from a first read operation to a secondread operation, the host 20 may know the data from the second readoperation). The host 20 may miss the data from the first read operation(e.g., the host 20 may miss some (e.g., the first) event information).

The RCD 74 may wait until there are any new assertions of the signalGSI_N. For any masked command that the RCD 74 has already issued, theremay not be further independent action taken by the RCD 74. For example,the RCD 74 may wait for further instruction from the host memorycontroller 20.

For the 2 events that comprise Response 3, the read response from thePMIC 100 may be updated in the RCD registers 194 (e.g., as shown inassociation with 3). For example, the RCD 74 may update the status inthe register PG82RW70 [7]. If PG82RW7F [0]=‘1’, the RCD 74 may generatea Write ‘1’ command to the corresponding Clear Bit Register location (asshown in Table 3) to clear the PMIC status register (e.g., indicatingthat the RCD 74 has deciphered which event caused the interrupt signalGSI_N). The RCD 74 may generate the Write ‘1’ command to the all 8 bitsof the corresponding Clear register to clear the entire 8 bits of thestatus register.

The Write ‘1’ command may cause the PMIC 100 to stop asserting theinterrupt signal GSI_N if there are no other events. The RCD 74 may wait(e.g., a maximum of 5 μs) to let the PMIC 100 stop assertion of thesignal GSI_N after generating the clear command. For example, the 5 μstime may be referenced from a rising edge of the clock when the RCD 74receives the acknowledge notification from the PMIC 100. At this pointthe RCD 74 may wait for any new assertions of the signal GSI_N.

The RCD 74 may assert the signal ALERT_N if PG82RW7F [7]=‘1’ and theinterrupt signal GSI_N is asserted. An amount of time for asserting thesignal ALERT_N may be based on whether the signal GSI_N is asserted for20 ns or less. The host memory controller 20 may read the error logregister (e.g., RW20 to RW24) to determine the cause of the signalALERT_N. If the signal ALERT_N is triggered due to the PMIC 100, thehost 20 can further read the status from page 0x82 (e.g., registers 0x68to 0x6B and 0x71). The signal ALERT_N may be persistent until the host20 sends the ‘Clear PMIC Error’ command.

When RCD 74 receives the ‘Clear PMIC Error’ command from the host 20,the RCD 74 may clear the GSI_N status in RW24 OP [0] and stop drivingthe signal ALERT_N (e.g., if the interrupt signal GSI_N is notasserted). If the interrupt signal GSI_N is still asserted when the RCD74 receives the ‘Clear PMIC Error’ command, the RCD 74 will continue toassert the signal ALERT_N and the RW24 OP [0] status bit may remain at‘1’.

If the memory modules 50 a-50 n are in a clock stopped power down mode,the RCD 74 may shut off the inputs and/or outputs 170 a-170 c (e.g., forthe signals SDA, SCL and GSI_N). For example, the RCD 74 may not takeany action during the clock stopped power down mode. However, there maybe some corner case conditions that occur as event interrupts as well asclock stopped power down mode events that may be truly random and/orasynchronous.

One corner condition may be that the RCD 74 detects the interrupt signalGSI_N and immediately after enters in the clock stopped power down mode.In response, the RCD 74 may assert the signal ALERT_N and maintain theassertion to the host 20. Since the interrupt handling process has notbeen started by the RCD 74, the RCD 74 may enter in the clock stoppedpower down mode and abort the interrupt handling process. The RCD 74 mayshut down the output 170 a (e.g., for SCL) and the I/O 170 b (e.g., forSDA). When the RCD 74 exits the clock stopped power down mode, theinterrupt handling process may be resumed.

One corner condition may be that the RCD 74 detects the interrupt signalGSI_N, starts an interrupt handling process and during the processenters the clock stopped power down mode. In response, the RCD 74 mayhave already asserted the signal ALERT_N and may maintain the assertionto the host 20. Since the RCD 74 may have already started the interrupthandling process, the RCD 74 may continue the interrupt handling processeven though the RCD 74 may have entered in the clock stopped power downmode. Once the RCD 74 completes the interrupt handling process, theoutput 170 a (e.g., for the signal SCL) and the I/O 170 b (e.g., for thesignal SDA) may be shut down. When the RCD 74 exits the clock stoppedpower down mode, the host 20 may be expected to resume normal operation.

One corner condition may be that the RCD 74 may be in the middle of aperiodic polling operation and enters in the clock stopped power downmode. In response, the RCD 74 may complete the polling operation. Oncethe RCD 74 completes the polling operation, the output 170 a (e.g., forthe signal SCL) and the I/O 170 b (e.g., for the signal SDA) may be shutdown.

One corner condition may be that the RCD 74 may be in the middle ofexecuting a PMIC Write/Read operation per a request from the host 20through the SMBus interface 350 and enters the clock stopped power downmode. In response, the RCD 74 may complete the PMIC write/readoperation. Once the read/write operation is complete, the output 170 a(e.g., for the signal SCL) and the I/O 170 b (e.g., for the signal SDA)may be shut down. Generally, it may be unlikely that the host 20 wouldmake a request through SMBus 350 for the PMIC 100 while at the same timeputting the RCD 74 in the clock stopped power down mode.

The RCD 74 may implement an arbitration scheme for when more than onerequest or event occurs simultaneously. For example, if the RCD 74 is inthe middle of executing any given operation when another request isreceived and/or another event happens, the RCD 74 may be configured tocomplete the operation before serving the new request/event. The RCD 74may arbitrate if there are more than one new requests/events. Generally,the RCD 74 may not abort the ongoing operation to serve another request.

The priority order when the RCD 74 receives a request from the host 20for a PMIC read/write operation at the same time when the periodicpolling timer expires and/or when the GSI_N interrupt event occurs isshown in Table 8. The priority order when the RCD 74 receives theinterrupt signal GSI_N at the same time as the periodic polling timerexpires in absence of request from the host 20 is shown in Table 9.

TABLE 8 Host Request Host Request & Normal Event & GSI Periodic Pollingwith Priority No GSI Interrupt Interrupt no GSI Interrupt 1 Host PMICRead Host PMIC Host PMIC Read Request Read Request Request 2 Host PMICWrite Host PMIC Host PMIC Write Request Write Request Request 3 PeriodicPolling GSI_N Periodic Polling Interrupt Handling 4 Periodic Polling

TABLE 9 Normal Event GSI Periodic Polling & Priority No GSI InterruptInterrupt No GSI Interrupt 1 Periodic Polling GSI_N Periodic PollingInterrupt Handling 2 Periodic Polling

In some embodiments, per registers PG82RW7F [7:6], the RCD-PMICinterface 102 may be disabled. At first power on, the host 20 may enablethe interface 102 by setting the bits to ‘1’. The host 20 may enableeither one or both registers. For example, if PG82RW7F [6]=‘1’, the host20 may also enable a low power optimization feature by setting PG82RW7F[2]=‘1’. In another example, if PG82RW7F [7]=‘1’, the host 20 may alsoset PG82RW7F [0]=‘1’ to generate a Write ‘1’ command to clear the statusof the interrupt signal GSI_N.

The RCD 74 may offer a clock stopped power down mode to reduce the powerconsumption of the memory modules 50 a-50 n when not in use. The powerconsumption during the clock stopped power down mode may be relativelysmall compared to the normal mode of operation of the memory modules 50a-50 n. The exit latency from clock stopped power down mode to the firstDRAM operation may be relatively large compared to normal mode.

If PG82RW7F [2]=‘1’, when the RCD 74 detects the clock stopped powerdown mode, the interrupt signal GSI_N may be pulled low (e.g., assertedto the PMIC 100 at the input 204 c). Providing the interrupt signalGSI_N to the PMIC 100 may communicate to the PMIC 100 that the memorymodule(s) 50 a-50 n are in the low power mode. In an example, the PMIC100 may check the GSI_N input 204 c when the PMIC 100 is not driving thesignal GSI_N low (e.g., to indicate an interrupt event). When PMIC 100detects the signal GSI_N, the PMIC 100 may adjust an operation mode tothe low power mode.

When the system host memory controller 20 takes the RCD 74 out of theclock stopped power down mode (e.g., by providing a valid input clock),the RCD 74 may stop driving the interrupt signal GSI_N input low. In anexample, the PMIC 100 may check the GSI_N input 204 c when the PMIC 100is not driving the signal GSI_N low. When the PMIC 100 detects that thesignal GSI_N is not low, the PMIC 100 may revert back to a normal (e.g.,original) mode.

When the RCD 74 is not driving the signal GSI_N low and detects theinterrupt signal GSI_N low at the input 170 c, the RCD 74 may treat theassertion as an interrupt event from the PMIC 100. When the PMIC 100 isnot driving the interrupt signal GSI_N low and detects the signal GSI_Nlow at the input 204 c, the PMIC 100 may treat the assertion as a lowpower mode entry. For example, in the low power mode, the PMIC 100 mayadjust the behavior characteristics of the voltage regulation modules228 a-228 f.

In a rare occasion when both devices pull the signal GSI_N low at thesame time, the RCD 74 may not take any action because the RCD 74 mayalready be in the clock stopped power down mode. When the RCD 74 exitsthe clock stopped power down mode, the signal GSI_N may be detected atthe input 170 c and the RCD 74 may handle the interrupt event. When boththe RCD 74 and the PMIC 100 assert the signal GSI_N, the PMIC 100 maynot enter in low power mode and may continue to operate as if a normalinterrupt has been asserted by the PMIC 100. When the RCD 74 and thePMIC 100 stops driving the interrupt signal GSI_N, both may wait (e.g.,a minimum 10 ns) before the GSI_N input to see if the other device hasasserted the signal GSI_N or not.

In some embodiments, at initial power on, the RCD 74 may optionallyperform the read operation to determine the exact voltage from theregulators 228 c-228 f and determine what the RCD 74 is receiving on theVDD input supply. The RCD 74 may optionally adjust and/or optimize theinternal circuitry without any help or knowledge by the host 20 for thatgiven DIMM design based on the voltage reading. Generally, the voltagereadout may not drift over temperature from V min to V max. The RCD 74may use the lack of drifting for tuning. To read the exact voltage fromthe PMIC 100 output, the RCD 74 may generate a read command to the PMIC100 to address R30 to see whether the host 20 has enabled the ADC. TheRCD 74 may store the result in a temporary memory. If the host 20 hasnot enabled the ADC, a write command to R30 may enable ADC and selectthe appropriate voltage rail. If the host 20 has enabled the ADC, then awrite command to R30 may be generated to select the appropriate voltage.A read command may be generated to the PMIC 100 (e.g., address 0x31) toread out the code. Similar steps may be repeated to read all appropriatevoltages. A write command may be generated to the PMIC 100 (e.g.,address R30) to restore original settings.

The RCD 74 (e.g., as a master) may only communicate standard I²Cprotocol to the PMIC 100 (e.g., as a slave) regardless of otherprotocols. For example, the host 20 (e.g., as a master) to RCD 74 (e.g.,as a slave) interface protocol may be either I²C or I³C. In an example,the PMIC 100 may have a 7-bit slave address (e.g., ‘1001000’) assumingthat the PID pin of the PMIC 100 is tied to GND on the PCB of the DIMM.The PMIC 100 may support at least four I²C bus commands. For example,the commands may be a Byte Write command, a Byte Read command, a BlockWrite command and a Block Read command.

Referring to FIG. 10, a method (or process) 500 is shown. The method 500may enable the RCD-PMIC interface 102. The method 500 generallycomprises a step (or state) 502, a step (or state) 504, a step (orstate) 506, a decision step (or state) 508, a step (or state) 510, astep (or state) 512, a step (or state) 514, a step (or state) 516, and astep (or state) 518.

The step 502 may start the method 500. In the state 504, the system(e.g., the host 20 and/or the memory modules 50 a-50 n) may be poweredon. In the state 506, the RCD-PMIC interface 102 may be disabled (e.g.,by default). Next, the method 500 may move to the decision step 508.

In the decision step 508, the host 20 may determine whether or not toenable the RCD-PMIC interface 102. If the host memory controller 20 hasnot enabled the RCD-PMIC interface 102, the method 500 may move to thestep 510. In the step 510, the components of the memory modules 50 a-50n (e.g., the RCD 74, the PMIC 100, etc.) may perform default operations.In the decision step 508, if the host memory controller 20 has enabledthe RCD-PMIC interface 102, the method 500 may move to the step 512.

In the step 512, the PMIC 100 may enable the RCD interface 220 a. In thestep 514, the RCD 74 may enable the PMIC interface 190. In an example,the steps 512-514 may be performed in parallel. Next, in the step 516,the RCD 74 may internally generate the clock signal SCL for the RCD-PMICinterface 102. Next, in the step 518, the components of the memorymodules 50 a-50 n may perform the default operations and/or theoperations using the RCD-PMIC interface 102.

Referring to FIG. 11, a method (or process) 550 is shown. The method 550may perform a PMIC read/write operation. The method 550 generallycomprises a step (or state) 552, a step (or state) 554, a step (orstate) 556, a step (or state) 558, a decision step (or state) 560, astep (or state) 562, a decision step (or state) 564, a step (or state)566, a step (or state) 568, a step (or state) 570, and a step (or state)572.

The step 552 may start the method 550. In the step 554, the counter 196implemented by the RCD 74 may be at zero (e.g., initialized). Next, inthe step 556, the RCD 74 may receive a PMIC command. For example, theRCD 74 may perform similar steps for a PMIC read operation or a PMICwrite operation. In the step 558, the RCD 74 may increment the counter196. Next, the method 550 may move to the decision step 560.

In the decision step 560, the RCD 74 may determine whether the counter196 has reset (e.g., looped back to zero). If the counter 196 has reset,the method 550 may move to the step 562. In the step 562, the RCD 74 mayloop back to the initial address of the pre-defined register space 194.Next, the method 550 may move to the decision step 564. In the decisionstep 560, if the counter 196 has not reset, the method 550 may move tothe decision step 564.

In the decision step 564, the RCD 74 may determine whether the commandfrom the host 20 has been stored at an even address. If the command isstored at an even numbered address, the method 550 may move to the step566. In the step 566, the RCD 74 may store a command that carries a PMICaddress. Next, the method 550 may move to the step 570. In the decisionstep 564, if the command is stored at an odd numbered address, themethod 550 may move to the step 568. In the step 568, the RCD 74 maystore a command that carries data to be stored at the address from theprevious (e.g., even numbered) command. Next, the method 550 may move tothe step 570.

In the step 570, the RCD 74 may start performing the operation (e.g., aread or write) on the RCD-PMIC interface 102. Next, in the step 572, theRCD 74 may update an operation completion status (e.g., update aregister when the operation has been completed). Next, the method 550may return to the step 556.

Referring to FIG. 12, a method (or process) 600 is shown. The method 600may perform a polling operation. The method 600 generally comprises astep (or state) 602, a step (or state) 604, a step (or state) 606, astep (or state) 608, and a step (or state) 610.

The step 602 may start the method 600. In the step 604, the RCD-PMICinterface 102 may be enabled (e.g., the enable command may have beenreceived by the RCD 74 and the PMIC 100 from the host memory controller20). Next, in the step 606, the RCD 74 may determine the pollingfrequency (e.g., read from the register PG82RW7E [7:5]). In the step608, the RCD 74 may internally generate the clock signal SCL. Next, inthe step 610, the RCD may perform the polling operations to poll datafrom the PMIC 100 using the RCD-PMIC interface 102. For example, the RCD74 may periodically poll the PMIC 100 according to the pollingfrequency.

Referring to FIG. 13, a method (or process) 650 is shown. The method 650may select a low power operation mode. The method 650 generallycomprises a step (or state) 652, a decision step (or state) 654, a step(or state) 656, a decision step (or state) 658, a step (or state) 660, adecision step (or state) 662, a step (or state) 664, and a step (orstate) 666.

The step 652 may start the method 650. In the decision step 654, thePMIC 100 may determine whether the PMIC 100 is asserting the interruptsignal GSI_N. If the PMIC 100 is asserting the interrupt signal GSI_N,the method 650 may move to the step 666. If the PMIC 100 is notasserting the interrupt signal GSI_N, the method 650 may move to thestep 656.

In the step 656, the PMIC 100 may check the GSI_N input 204 c. Forexample, the PMIC 100 may only check the input 204 c when the PMIC 100is not driving the interrupt signal GSI_N low. Next, the method 650 maymove to the decision step 658. In the decision step 658, the PMIC 100may determine whether the RCD 74 has asserted the interrupt signalGSI_N. If not, the method 650 may move to the step 666. If the RCD 74has asserted the interrupt signal GSI_N, the method 650 may move to thestep 660.

In the step 660, the PMIC 100 may adjust the operation for low powermode. Next, the method 650 may move to the decision step 662. In thedecision step 662, the PMIC 100 may determine whether the interruptsignal GSI_N is still present (e.g., still being asserted by the RCD74). If the interrupt signal GSI_N is still present, the method 650 mayreturn to the step 660. If the interrupt signal GSI_N is not present,the method 650 may move to the step 664. In the step 664, the PMIC 100may revert to the original (e.g., default) operating mode. Next, themethod 650 may move to the step 666. The step 666 may end the method650.

Referring to FIG. 14, a method (or process) 700 is shown. The method 700may perform a response type to an interrupt signal. The method 700generally comprises a step (or state) 702, a step (or state) 704, adecision step (or state) 706, a step (or state) 708, a decision step (orstate) 710, a step (or state) 712, a decision step (or state) 714, astep (or state) 716, a decision step (or state) 718, a step (or state)720, and a step (or state) 722.

The step 702 may start the method 700. In the step 704, the RCD 74 mayread the event status. Next, the method 700 may move to the decisionstep 706. In the decision step 706, the RCD 74 may determine whether theinterrupt event has been deciphered. If not, the method 700 may returnto the step 704. If the event has been deciphered, the method 700 maymove to the step 708.

In the step 708, the RCD 74 may write to the clear bit registers. Next,the method 700 may move to the decision step 710. In the decision step710, the RCD 74 may check the input 170 c to determine whether theinterrupt signal GSI_N is still being asserted by the PMIC 100. If not,the method 700 may move to the step 720. If the interrupt signal GSI_Nis still being asserted, the method 700 may move to the step 712.

In the step 712, the RCD 74 may read the event status. Next, the method700 may move to the decision step 714. In the decision step 714, the RCD74 may determine whether the event is still the same. If not, the method700 may return to the step 708. If the event is still the same, themethod 700 may move to the step 716.

In the step 716, the RCD 74 may write to the mask registers. Next, themethod 700 may move to the decision step 718. In the decision step 718,the RCD 74 may check the input 170 c to determine whether the interruptsignal GSI_N is still being asserted by the PMIC 100. If the interruptsignal GSI_N is still being asserted, the method 700 may move to thestep 722. In the step 722, the RCD 74 may assume that the interruptevent indicated by the PMIC 100 is a new event. Next, the method 700 mayreturn to the step 704. In the decision step 718, if the interruptsignal GSI_N is not still asserted, the method 700 may move to the step720. The step 720 may end the method 700.

Referring to FIG. 15, a method (or process) 750 is shown. The method 750may respond to an interrupt event. The method 750 generally comprises astep (or state) 752, a step (or state) 754, a decision step (or state)756, a step (or state) 758, a step (or state) 760, a step (or state)762, a step (or state) 764, and a step (or state) 766.

The step 752 may start the method 750. In the step 754, the RCD-PMICinterface 102 may be enabled (e.g., the enable command may have beenreceived by the RCD 74 and the PMIC 100 from the host memory controller20). Next, the method 750 may move to the decision step 756.

In the decision step 756, the RCD 74 may check the input 170 c todetermine whether the interrupt signal GSI_N has been detected. If not,the method 750 may move to the step 758. In the step 758, the RCD 74 maypoll data from the PMIC 100 according to the polling frequency and/orperform default operations (e.g., as shown in association with FIG. 12).In the decision step 756, if the interrupt signal GSI_N has beendetected, the method 750 may move to the step 760.

In the step 760, the RCD 74 may assert the signal ALERT_N to the hostmemory controller 20. Next, in the step 762, the RCD 74 may generate aread command to the PMIC 100 using the RCD-PMIC interface 102. In thestep 764, the RCD 74 may complete any current and/or ongoing operation.Next, in the step 766, the RCD 74 may perform the event interruptresponse.

Although embodiments of the invention have been described in the contextof a DDR5 application, the present invention is not limited to DDR5applications, but may also be applied in other high data rate digitalcommunication applications where different transmission line effects,cross-coupling effects, traveling wave distortions, phase changes,impedance mismatches and/or line imbalances may exist. The presentinvention addresses concerns related to high speed communications,flexible clocking structures, specified command sets and lossytransmission lines. Future generations of DDR can be expected to provideincreasing speed, more flexibility, additional commands and differentpropagation characteristics. The present invention may also beapplicable to memory systems implemented in compliance with eitherexisting (legacy) memory specifications or future memory specifications.

The terms “may” and “generally” when used herein in conjunction with“is(are)” and verbs are meant to communicate the intention that thedescription is exemplary and believed to be broad enough to encompassboth the specific examples presented in the disclosure as well asalternative examples that could be derived based on the disclosure. Theterms “may” and “generally” as used herein should not be construed tonecessarily imply the desirability or possibility of omitting acorresponding element.

While the invention has been particularly shown and described withreference to embodiments thereof, it will be understood by those skilledin the art that various changes in form and details may be made withoutdeparting from the scope of the invention.

1. An apparatus comprising: a host interface configured to receivecontrol words from a host; and a power management interface configuredto (i) enable said host to read/write data from/to a power managementcircuit of a dual in-line memory module, (ii) communicate said data,(iii) generate a clock signal and (iv) communicate an interrupt signal,wherein (a) said power management interface is disabled at power on, (b)said apparatus is configured to (i) decode said control words, (ii)enable said power management interface when said control words providean enable command and (iii) perform a response to said interrupt signaland (c) said clock signal operates independently from a host clock. 2.The apparatus according to claim 1, wherein said apparatus implements aregistered clock driver on said dual in-line memory module.
 3. Theapparatus according to claim 1, wherein said apparatus is configured topoll said data from said power management circuit periodically.
 4. Theapparatus according to claim 1, further comprising a pre-definedregister space, wherein said data is stored in said pre-defined registerspace.
 5. The apparatus according to claim 4, wherein said control wordsenable said host to read from and write to said pre-defined registerspace.
 6. The apparatus according to claim 5, wherein said control wordsthat are written to even numbered addresses of said pre-defined registerspace provide an address of said power management circuit for at leastone of a read operation and a write operation.
 7. The apparatusaccording to claim 5, wherein said control words that are written to oddnumbered addresses of said pre-defined register space provide said datafor at least one of a read operation and a write operation.
 8. Theapparatus according to claim 5, further comprising a counter, whereinsaid counter is configured to track said control words.
 9. The apparatusaccording to claim 1, further configured to perform a response type whensaid interrupt signal is received, wherein said response type comprises(a) no response in a first mode, (b) masking a register and waiting forsaid host to decide in a second mode and (c) clearing said register in athird mode.
 10. The apparatus according to claim 1, wherein saidapparatus generates said interrupt signal to communicate that said dualin-line memory module is in a low power state.
 11. The apparatusaccording to claim 1, wherein operating said clock signal independentlyfrom said host clock enables said apparatus to generate and respond tocommands regardless of a state of said host clock.
 12. The apparatusaccording to claim 1, further configured to generate an alert signal,wherein (a) said alert signal is presented to said host in response toreceiving said interrupt signal, (b) said host reads an error logregister of said apparatus in response to said alert signal and (c) saidalert signal is asserted until a clear command is received from saidhost.
 13. The apparatus according to claim 1, wherein said powermanagement interface implements a master I²C protocol.
 14. The apparatusaccording to claim 1, wherein said apparatus is configured using a JEDECstandard pinout in addition to (i) a pin for said data, (ii) a pin forsaid clock signal and (iii) a pin for said interrupt signal.
 15. Theapparatus according to claim 1, wherein said data comprises a powermeasurement readout, a current consumption measurement readout, a statusof said apparatus, a temperature readout.
 16. The apparatus according toclaim 1, wherein said power management interface is configured to enablebi-directional communication of said data.
 17. The apparatus accordingto claim 1, wherein said power management interface reduces an amount ofbandwidth in a host bus used by said dual in-line memory module.
 18. Theapparatus according to claim 1, wherein said power management interfacereduces a readout time latency of said data compared to using a hostbus.
 19. The apparatus according to claim 1, wherein said dual in-linememory module is implemented according to a double data ratefifth-generation synchronous dynamic random-access memory (DDR5 SDRAM)standard.